The latest updates on your projects. Learn more about Vercel for Git ↗︎

Upon saving & reloading a project, then updating the toolbox (switching to costume editor or switching sprites), strange things can happen with sprite-only timers. The code editor also crashes if you load the project twice(?) [images]

First one, I can't replicate. (I didn't do the steps correctly)

That's... odd. Seems to be that somehow the "name" property never got initialized. I'll have to look a little more into that, I'm not sure how it wouldn't be initialized.

I think I fixed the crash by just copying more from the XML escape utility.

Still haven't replicated the strange behavior with for this sprite timers. I think I fixed both of them with that last push... I think.

you might want to add a warning on the extension page for it (you cant set value background color)

Is there a specific JSON key for marking incompatibility? Incompatibility doesn't mean it's really unstable IMO.

@JeremyGamer13

Shouldn't be incompatible anymore.

Only built-in blocks are able to set themselves as per-sprite, so every time any block in this extension is run anywhere, it always assumes that the variables are global, so util.target returns the editing target...

Actually, I'm not quite sure if that's the actual issue you were experiencing before.

• Upon saving & reloading a project, then updating the toolbox (switching to costume editor or switching sprites), strange things can happen with sprite-only timers

Weirdly enough, I'm not sure this is a fault in my extension.

I haven't seen anything being switched to being local, but I have seen timers being duplicated, literally duplicated but with an ID of undefined.

Yeah, it seems to be existing on load.

Yeah, it seems to be existing on load.

Could still be an issue with my stuff, I'll try some other stuff with my extension.

Incompatibility doesn't mean it's really unstable IMO.

It's really just an extension warning label, it's named unstable since that's the most common reason for it to be on an extension

It's really just an extension warning label, it's named unstable since that's the most common reason for it to be on an extension

Either way, it's not incompatible anymore.

Not sure what's causing this anymore but saving the project, loading it again and reloading the toolbox makes timers called "undefined" appear. They get renamed to "null" after saving again and reloading

Not sure what's causing this anymore but saving the project, loading it again and reloading the toolbox makes timers called "undefined" appear. They get renamed to "null" after saving again and reloading

Couldn't replicate that, so I can't really fix it 🤷

I think... I fixed it... maybe